Installing MacsBug:

Copy the files MacsBug and "Debugger Prefs" to the System folder on your
boot disk and reboot.  The MacsBug file is required.  The "Debugger Prefs"
file is optional.  It contains macros, templates and other MacsBug resources
that are loaded if present.



Installing MacsBug to minimize RAM usage:

Copy the files MacsBug to the System folder on your boot disk.  Use ResEdit
to remove the 'mxbh' resource (help text) from the MacsBug file that you just
copied.  Make sure there is not a debugger prefs file in your System folder.
Reboot.



What the Resources folder contains:

This folder contains the following resources that can be pasted into the
Debugger Prefs file to increase MacsBug functionality.

	Floating Point		Macros to support A-Trap breaks at FP68K calls
	HFS Calls			Macros to support A-Trap breaks at HFSDispatch calls
	List Manager		Macros to support A-Trap breaks at Pack0 calls
	C++					Code to unmangle C++ names
	KCHR				The key map to use for the MacsBug keyboard.
						  This is used to debug international software.

The folder "MPW .r files" contains the text that was used to create the
MacsBug resources.  Templates.r,  Macros.r,  Init.r and Color.r  are shipped
as resources in the Debugger Prefs file since they are commonly used.
FloatingPoint.r, HFSCalls.r and ListManager.r are shipped as separate
resources since they are not as widely used.



What the dcmds folder contains:

This folder contains a sample dcmd written in both C and Pascal.  These
folders contain the source code,  the dcmd interface (.h and .p respectively),
a glue file to be linked with each dcmd and an MPW tool to convert the linked
application into a dcmd.

This folder also contains an application, Test dcmd, that simulates the MacsBug
environment while testing your dcmd's.  This allows you to use MacsBug while
debugging a dcmd.

Finally,  this folder contains contributed dcmds. Information about each one is
available in MacsBug by typing "HELP name".
